Summary

Fixes two issues that occur when running multiple JavaScript adapter instances:

Problem 1: Duplicate "Stopping script" log messages
When stopScript() was called for a script that was not running on the current instance, it would still log Stopping script and attempt to set the scriptEnabled state — even though there was nothing to stop. This caused confusing duplicate log entries.

Fix: Added an early return in stopScript() that checks this.scripts[name] before proceeding. If the script is not loaded on this instance, it returns false immediately without logging or side effects.

Problem 2: Unnecessary script restarts on unrelated instances
When a script's source code was changed (e.g., saved in the editor), the onObjectChange handler would trigger a stop/restart cycle on every JavaScript adapter instance — not just the one that owns the script. This led to unnecessary restart attempts and confusing log output on instances that don't run the script.

Fix: Changed the unconditional else branch in onObjectChange to an else if that checks whether the script's engine (current or former) matches system.adapter.${this.namespace}. Only the owning instance now reacts to source changes.

Changes

• src/main.ts: Early return in stopScript() when script is not running
• src/main.ts: Instance-scoped restart in onObjectChange for script source changes
• build/main.js: Compiled output matching the source changes
• README.md: Changelog entries under WORK IN PROGRESS

Test plan

• Start two JavaScript adapter instances (e.g., javascript.0 and javascript.1)
• Assign a script to javascript.0, save/edit it
• Verify only javascript.0 logs "Stopping script" / restart — javascript.1 stays silent
• Disable a script and verify no duplicate "Stopping" messages appear
• npm run test passes (41 integration tests)
• npm run lint passes on src/main.ts

🤖 Generated with Claude Code